Security News
UK Officials Consider Banning Ransomware Payments from Public Entities
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Returns all environment variables with sensitive values hidden, great for logs
Returns all environment variables with sensitive values hidden, great for logs
When you start the server, and something does not work, are you sure that all expected environment variables were set correctly? Can you quickly dump them to a console or send them to the logging service? Can you hide the sensitive information, like passwords or tokens?
const safeEnv = require('safe-env')
const sensitive = ['TOKEN', 'API-KEY']
console.log(safeEnv(sensitive))
/*
{
FOO: 'foo value',
BAR: 'bar value',
TOKEN: '<hidden>'
}
*/
Seems we forgot to set API-KEY
!
You can pass an object to be filtered instead of using process.env
const result = safeEnv(sensitive, myObject)
process.env
are printed,
filtering out lots of noise, like npm_...
keys.You can pass a custom predicate function that returns true based on the property name to filter custom values. For example to hide all properties with string 'token' in them
const o = {
foo: 42,
myToken: 'secret',
'another-token': 'very secret'
}
const tokenName = (key) => key.toLowerCase().indexOf('token') !== -1
const out = safeEnv(tokenName, o)
// out has both 'myToken' and 'another-token' values replaced
// with '<hidden>'
Author: Gleb Bahmutov <gleb.bahmutov@gmail.com> © 2016
License: MIT - do anything with the code, but don't blame me if it does not work.
Support: if you find any problems with this module, email / tweet / open issue on Github
Copyright (c) 2016 Gleb Bahmutov <gleb.bahmutov@gmail.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Returns all environment variables with sensitive values hidden, great for logs
The npm package safe-env receives a total of 930 weekly downloads. As such, safe-env popularity was classified as not popular.
We found that safe-env demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.